V408 -- BG2 native Saved Game import through character creation (V406 base)

REQUESTED FLOW
    Character Creation > Import > Saved Game
        -> native saved-game LOAD screen
        -> autoselect exact native save FOLDER 000000001-<logged-in Accountname>
        -> user clicks LOAD
        -> native CHARACTER_SELECT from the selected BG2 saved game (.GAM/.SAV).

Example: Drakhysys -> 000000001-Drakhysys; Kronas -> 000000001-Kronas.
Account names must match case-sensitively. If the exact #1 slot is missing, the
newest engine-listed <digits>-<Accountname> slot can be selected. The importer
never guesses a file path or loads other accounts' games. No auto-click.

INSTALL
    Close BG2. Extract archive. Run:
    All Editors/APPLY_V408_CHARACTER_SAVED_GAME_IMPORT_UI_ONLY.bat
    Pick the folder with BaldurII.exe, or supply it as a quoted BAT parameter.
    The installer updates ONLY BG2/override/UI.MENU. It restores read-only
    state after a successful atomic swap. It does not reinstall account setup.

LIMITATIONS
    A UI.MENU script cannot direct BG2's native save enumerator to a different
    root. The BG2 engine must expose the desired /save/ folder to its native
    character-import Saved Game dialog. In multiplayer, the engine may use
    /mpsave/ instead. If this happens, no save is loaded; the script will not
    copy or create files or force a potentially crashing engine load.
    In-game transition to CHARACTER_SELECT needs verification in BG2; syntax,
    installer and offline mocked engine behavior are tested only.

SAFETY
    Native CHR import is not called in this route. Full campaign Load Game
    and existing V406 multiplayer character replacement are preserved.
    The UI still shows native engine-listed saves; loading another account's
    saved game is blocked in the Import Saved Game branch.
